Skip to content

ci: allow pr-shepherd: label prefix in PR label validation#12063

Closed
mikewoo-dd wants to merge 1 commit into
DataDog:masterfrom
mikewoo-dd:allow-pr-shepherd-label-prefix
Closed

ci: allow pr-shepherd: label prefix in PR label validation#12063
mikewoo-dd wants to merge 1 commit into
DataDog:masterfrom
mikewoo-dd:allow-pr-shepherd-label-prefix

Conversation

@mikewoo-dd

Copy link
Copy Markdown

What

Add the pr-shepherd: prefix to the validCategories allowlist in check-pull-request-labels.yaml.

Why

The PR Shepherd automation applies labels such as pr-shepherd:in_progress. The Validate PR Label Format workflow only accepts labels matching a fixed set of prefixes, so these labels were flagged as invalid and the PR was blocked (a maintainer had to delete the bot comment to unblock). See e.g. #12034 (comment)

Consequence check

  • validCategories is read in exactly one place (this filter); nothing else consumes it.
  • No other workflow acts on a pr-shepherd: label — check-pull-requests.yaml requires type:/comp:/inst:, and draft-release-notes-on-tag.yaml only maps comp:/inst: (any pr-shepherd: label falls through to "other PRs").
  • No test fixtures reference the prefix list.

The change only removes the false-positive block; no downstream side effects.

🤖 Generated with Claude Code

The PR Shepherd automation applies labels like `pr-shepherd:in_progress`,
which the label validator rejected as invalid and blocked the PR. Add the
`pr-shepherd:` prefix to the allowlist so these labels no longer trigger a
block.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

@PerfectSlayer PerfectSlayer left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please don't. Those checks were set on purpose to limit the tag addition for every new tools that keep being added quarter over quarter and are never taken care of after.
I would invite you to describe the need first, then we can define a set of labels for the tool if needed that will fit the repository conventions.
Additionally, the PR does not explain the motivation. It only states "I'm blocked, so I'm lifting enforcement".

@PerfectSlayer

Copy link
Copy Markdown
Contributor

I keep reading at PR sherper and this is actually a good thing that PRs are blocked:

PR Shepherd (…) works out what to do, and pushes needed fixes straight to your branch

We require contributors and reviewers to read and acknowledge any code changes. We don't want a bot to write and push code without supervision as the code is running on customer infrastructure and applications.

@mikewoo-dd mikewoo-dd closed this Jul 24, 2026
@mikewoo-dd
mikewoo-dd deleted the allow-pr-shepherd-label-prefix branch July 24, 2026 14:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants